home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CU Amiga Super CD-ROM 27
/
CU Amiga Magazine's Super CD-ROM 27 (1998)(EMAP Images)(GB)[!][issue 1998-10].iso
/
CUCD
/
Sound
/
SPlayer
/
Socks5
/
examples
/
single_homed_host.example
< prev
next >
Wrap
Text File
|
1997-06-18
|
4KB
|
89 lines
File Name: single_homed_host.example
1. Example - Single-homed Host with Kerberos Authentication
# This example describes a socks5 environment on network 163.201.56., with:
# - one socks5 server, serverA running with kerberos authentication
# - one socks5 client, clientA, running with Kerberos authentication
#
# This example assumes the socks5 client and server were built with
# Kerberos --with-krb5[=path]. For more information about the krb5 option,
# see the INSTALL and README files.
#
# The client has one socks5 user, userA, who can issue all commands to any
# destination on the 163.201.56. network.
# The user must perform kinit before running commands to socks5 servers.
--------- --------------- ----------
| serverA | | 163.201.56. | | clientA |
| |-------| Network |-------| |
--------- --------------- ----------
| userA: unix user id
| userA@compA.ker.id: Kerberos user id
-------------
| Destination |
| any host on |
| 163.201.56. |
-------------
2. Server Environment Variables
# You must tell the server where to find the configuration file. You can do so
# in one of three ways:
# - Set the environment variable SOCKS5_CONFFILE
# - Include the socks5.conf file in the default directory, usually /etc
# - Build with the --with-srvconffile=path option
# This example demonstrates using environment variables. The example path is
# arbitrary.
setenv SOCKS5_CONFFILE /socksdir/run/socks5.conf
3. Server Configuration File socks5.conf
# This is the socks5.conf file for a single-homed host with Kerberos
# authentication. socks5.conf must be in the directory specified in the
# socks5 environment variable SOCKS5_CONFFILE, or the default directory,
# /etc/socks5.conf. The valid Kerberos id for userA is, userA@compA.ker.id
auth 163.201.56. - k
permit k - 163.201.56. 163.201.56. - - userA@compA.ker.id
4. Runtime mode
# To add debugging to any of these commands, add the following options:
# -d 2 -s
#
# To start the server in standalone mode on bindport 3000, at the
# command prompt, type:
# ./socks5 -b 3000
#
# To start the server in preforking mode on bindport 3000 with 8 child
# processes, at the command prompt, type:
# ./socks5 -b 3000 -p -n 8
#
# If you built with threads, by adding the the --with-threads [=path]option, to
# start the server in threaded mode on bindport 3000, at the command prompt,
# type:
# ./socks5 -b 3000 -t
5. Client Configuration File libsocks5.conf
# When the client and server are on the same network, it is most efficient to
# omit the client configuration file and allow the client to connect directly
# to the server. We include the configuration file for the purpose of
# demonstration.
#
# This is the libsocks5.conf configuration file for clientA. It should be in the
# directory specified in the build, or in the default directory, usually /etc
socks5 - 163.201.56. - userA serverA:3000 #userA is the unix user ID
# When you include a configuration file, set the client environment variable
setenv SOCKS5_NONETMASKCHECK
# When you omit the configuration file, set the SOCKS5_SERVER environment
# variable:
setenv SOCKS5_SERVER serverA:3000